Add a new handoff section under cloud-agents that documents the three
directions of handoff supported by the orchestration launch:

- Overview (conceptual) explaining what handoff is, the three
  directions, and what carries over.
- Local→cloud (procedural) for promoting a local Warp Agent
  conversation to a cloud agent run.
- Cloud→local (procedural) for picking up a cloud run inside the
  Warp terminal via /continue-locally and equivalent UI entrypoints.
- Cloud→cloud (procedural) for follow-ups that span multiple
  executions of the same run.

Co-Authored-By: Oz <oz-agent@warp.dev>

Address PR review feedback and Slack-thread direction.

- Drop cloud-to-local.mdx; existing fork-to-local docs in
  viewing-cloud-agent-runs.mdx already cover the capability. Overview
  now references that page for cloud-to-local.
- Scope the snapshot rehydration mechanism in the overview to
  local-to-cloud and cloud-to-cloud only; cloud-to-local does not
  apply workspace patches.
- Replace the inaccurate `git diff --binary HEAD` capture description
  in local-to-cloud with a high-level summary that covers tracked and
  untracked changes without committing to a specific git command.
- Soften the local-to-cloud entry point: do not document a specific
  keyboard shortcut, add a note that the affordance may evolve during
  the Oz launch rollout.
- Strip internal-only details from user-facing copy: GCS paths,
  manifest filenames, `git apply` mechanics, internal routing names
  (appended/injected/requeued), API endpoint paths, and rehydration
  checklist references.
- Senior-writer pass: tighten descriptions to 50-160 chars, reduce
  marketing fluff, normalize cross-references.

Co-Authored-By: Oz <oz-agent@warp.dev>

- Replace 'execution' with 'session' across cloud-to-cloud.mdx so the
  user-facing unit of work stays 'the run', not the internal model.
- Drop 'rehydrate'/'rehydration' in favor of 'restore'/'carry over';
  fold the standalone 'Rehydration behavior' section into 'What carries
  over' in the overview.
- Drop the 'server-side' qualifier on 'fork' throughout; users don't
  care where the fork happens.
- Collapse the cloud-to-cloud 'How follow-ups route' state-machine
  into a single user-facing description; remove the two routing-paths
  items from troubleshooting since they describe normal behavior, not
  problems.
- Collapse local-to-cloud's 'Verifying the handoff' debugging
  walkthrough into one sentence pointing readers to the management
  view.
- Cut meta self-descriptions: 'The handoff entry point is integrated
  into the cloud agent launch flow...' and 'Cloud-to-cloud handoff is
  automatic...'.
- Drop the rollout caveat note on local-to-cloud.
- Reduce 'sandbox' references where they leak infrastructure.

Co-Authored-By: Oz <oz-agent@warp.dev>

Co-Authored-By: Oz <oz-agent@warp.dev>

- cloud-to-cloud.mdx: soften per-session timeline claim to API-only (UI render not present)
- cloud-to-cloud.mdx: gloss 'ambient agent task' inline for clarity
- local-to-cloud.mdx: switch primary credits link to credits page; fix link text casing for access page

Co-Authored-By: Oz <oz-agent@warp.dev>

- index.mdx: drop launch-anchored framing; reframe Directions list as
  evergreen capability statement; add third-party-harness coverage
  subsection (cloud<->cloud works on 3P with Continue+input prompt;
  local->cloud is Warp Agent only).
- local-to-cloud.mdx: replace /cloud-agent entry-point claim with the
  '&' shortcut and the '/handoff' slash command; add note that the
  model can't be changed during handoff.
- cloud-to-cloud.mdx: consolidate duplicate scheduled/integration
  bullets; add 'same Git branch' detail to workspace-state carryover;
  add :::caution that handoff requires a prior-execution snapshot;
  note that local->cloud-originated runs can only be continued by
  the creating user; scope send-follow-up to the Warp app and drop
  the Oz-web-app/integration follow-up sections; add third-party
  harness Continue-button flow; soften per-execution timeline claim
  (transcript is the source of truth, not the API).

Co-Authored-By: Oz <oz-agent@warp.dev>

…cloud.mdx

Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com>

Apply all 9 of @rachaelrenk's suggested edits on PR #85 and run a final
senior-copywriter pass for consistency across the three handoff pages.

index.mdx
- Intro: "your local Warp terminal" -> "a local Warp session" so the
  intro talks about a session rather than the terminal application.
- "Third-party harness coverage" -> "Third-party agent runtime
  coverage"; same swap in the two bullets underneath. "Harness" is
  internal vocabulary; "agent runtime" is the user-facing term.
- "spiraled into work" -> "grown into work" (less idiomatic).
- "Managing Cloud Agents" -> "Managing cloud agents" in Related pages
  to match the sentence-case nav style used elsewhere.
- Consistency polish: "Fork a cloud conversation into your local
  terminal" -> "into a local Warp session" so the cloud-to-local
  bullet uses the same terminology as the rewritten intro.

local-to-cloud.mdx
- Intro: "Hand off a conversation from the Warp terminal" -> "Hand off
  a local Warp conversation" (same reason as above).
- "This direction is the right move when:" -> "Use this handoff
  direction when:" (less conversational, matches docs voice).
- Post-handoff pointer: linked the management view doc -> deep-linked
  the [Runs page](https://oz.warp.dev/runs) in the Oz web app, which
  matches the pattern added in PR #84.
- "Cloud Agents quickstart" -> "Cloud agents quickstart" (sentence
  case).

cloud-to-cloud.mdx (consistency polish, same patterns Rachael called
out in the other two pages)
- "This direction is the right move when:" -> "Use this handoff
  direction when:".
- Step 1 of "Sending a follow-up": linked the management view doc ->
  deep-linked the Runs page in the Oz web app.
- Removed a stray duplicate `### Third-party harnesses` heading that
  was sitting directly above the correct `### Third-party agent
  runtimes` heading, and inserted a missing blank line before the
  next `## Inspecting a run that's been handed off` section.
- "Managing Cloud Agents" -> "Managing cloud agents" in Related pages.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues.
- python3 .agents/skills/check_for_broken_links/check_links.py --internal-only
  -> 0 broken links (2,439 internal links across 321 files).

Co-Authored-By: Oz <oz-agent@warp.dev>

A senior-copywriter follow-up on commit b45a4e8. Focuses on terminology
consistency, list parallelism, active voice, and a few style-guide nits
caught on the second read.

index.mdx
- Frontmatter description: "Move an agent conversation between your
  terminal and the cloud" -> "Move agent work between a local Warp
  session and the cloud" so the description matches the body intro
  (which Rachael's review moved to "local Warp session" terminology).
- "Directions of handoff" Local-to-cloud bullet: "more compute,
  longer-running work, or to fan out variants in parallel" ->
  "more compute, longer-running work, or parallel variants of the
  same task". Now all three list items are parallel noun phrases.
- "Workspace state" bullet: "The cloud-to-local direction does not
  currently apply" -> "doesn't currently apply" (contractions are
  encouraged in the style guide for an approachable tone).

local-to-cloud.mdx
- "Use this handoff direction when:" list: first bullet started with
  "The task is going to run for a long time..." while the other three
  start with "You want...". Rewrote it to "You have a long-running
  task and don't want to keep your laptop awake." so all four bullets
  open the same way.
- Step 1: "trigger handoff with the `&` shortcut or the `/handoff`
  slash command" -> "press `&` or run the `/handoff` slash command".
  Direct verbs match the style guide pattern for keyboard / slash
  commands.
- Step 2: "Pick the environment whose..." -> "Pick the one whose..."
  (avoids repeating "environment" right after the bold header).
  "create one first and add" -> "create one and add" ("first" was
  doing no work).
- Post-steps prose: "After submission, the cloud agent applies your
  workspace snapshot" -> "After you submit, the cloud agent...".
  Active voice; readers don't talk about "submission."
- Troubleshooting (uncommitted changes): "Without it, the
  conversation can't be forked" -> "Otherwise, the conversation can't
  be forked". "Without it" had a fuzzy antecedent; "Otherwise" reads
  cleanly off the preceding sentence.

cloud-to-cloud.mdx
- "Use this handoff direction when:" list: first bullet "A cloud
  agent finished and you want to send a follow-up after the session
  has ended." -> "You want to send a follow-up to a cloud agent
  after its session has ended." Now parallel with the second bullet
  ("You want to continue an ambient agent run...").
- Cleaned up three lingering uses of "execution" that the earlier
  internals scrub missed. All three were re-introduced when applying
  Safia's audit-fix feedback in e4bdd4b. Replaced with "session":
    - "the new execution runs on the same Git branch as the prior
      session" -> "the new session continues on the same Git branch"
      (avoids both the internal term and the "new ... prior" cycle).
    - ":::caution Cloud-to-cloud handoff relies on a snapshot from
      the prior execution" -> "...the prior session".
    - "Click into the run to see the full transcript: each
      execution appears in order, and you can scan the transcript to
      see where one execution ended and the next began. Per-execution
      timestamps aren't currently exposed in the API..." -> all three
      "execution"s -> "session" / "Per-session".
- "What carries over" trailing sentence: "...proceeds with what it
  could before continuing to your follow-up." -> "...rather than
  starting over silently." Now parallel with the same sentence on
  the other two handoff pages.
- "Sending a follow-up" lead-in: dropped the orphan third sentence
  ("Send-follow-up support is available in the Warp app.") and
  folded it into the first: "you send a follow-up from the Warp app,
  and the run continues."
- Step 2: "Type the next message into the conversation's input" ->
  "Enter the next message in the conversation's input" ("Enter" is
  the style guide's verb for text fields).
- Troubleshooting (old runs): "Start a new cloud agent run with the
  prompt you want and reference the prior run in the prompt if
  needed." -> "Start a new cloud agent run with the prompt you want,
  referencing the prior run if needed." (drops the "prompt"
  repetition).

Final grep over the handoff folder for "execution", "harness",
"spiraled", "right move", "Cloud Agents", "Warp terminal" -> zero hits.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues.
- python3 .agents/skills/check_for_broken_links/check_links.py --internal-only
  -> 0 broken links (2,439 internal links across 321 files).

Co-Authored-By: Oz <oz-agent@warp.dev>

I missed two of @rachaelrenk's review comments on the cloud-to-cloud
page in earlier passes because they weren't returned by the first
`gh pr view` query. Applying them now.

cloud-to-cloud.mdx
- "ambient agent run" -> "background cloud agent run". Rachael flagged
  "ambient agent run" as abstract/internal-feeling; "background cloud
  agent run" keeps the example concrete and matches the user-facing
  framing on the surrounding pages. Per her suggested edit verbatim.
- Removed `blocked` from the example list of terminal states. The API
  treats BLOCKED as terminal for cancellation purposes, but the spec
  describes it as "awaiting user input or approval" — so it isn't a
  natural place to send a follow-up via cloud-to-cloud handoff
  (responding to the prompt on the original run is the right path).
  Added a sentence to the prereq calling that out explicitly so
  readers don't try to hand off a blocked run.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues.
- python3 .agents/skills/check_for_broken_links/check_links.py
  --internal-only -> 0 broken (2,439 internal links, 321 files).

Co-Authored-By: Oz <oz-agent@warp.dev>

Two small consistency fixes caught on a third audit round:

- L29 "An ended cloud agent run" prereq: "Blocked runs ... aren't
  continued through cloud-to-cloud handoff" -> "...can't be continued
  via cloud-to-cloud handoff". Makes the carve-out parallel with the
  very next sentence ("Very old runs ... can't be continued via
  handoff"), and reads more directly than "aren't continued through".
- L30 "A snapshot from the prior session" prereq: "the run still
  continues -- it just starts without restored workspace state" ->
  "the run still continues, just without restored workspace state".
  The em dash + "it just starts" was colloquial and a bit redundant
  ("continues" and "starts" describe the same event); the comma-led
  adjective phrase is cleaner.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues.
- python3 .agents/skills/check_for_broken_links/check_links.py
  --internal-only -> 0 broken (2,439 internal links, 321 files).

Co-Authored-By: Oz <oz-agent@warp.dev>

The "cross-cutting sidebar PR" that the original PR description referred
to doesn't exist — none of the orchestration-launch content is currently
registered in `src/sidebar.ts`. PR #84 (multi-agent) doesn't touch the
sidebar either; only PR #86 (memory) adds its own entries. Following
that pattern: register the three handoff pages here so they actually
appear in the docs sidebar when this branch merges.

src/sidebar.ts
- Added a new "Handoff" collapsible group inside the "Oz Cloud Agents
  & Orchestration" topic, slotted right after "Viewing cloud agent
  runs" since that's the closest thematic neighbor (it covers
  `Continue locally` / `/continue-locally`, the cloud-to-local path).
  The group contains:
    - Overview -> agent-platform/cloud-agents/handoff
    - Local to cloud -> agent-platform/cloud-agents/handoff/local-to-cloud
    - Cloud to cloud -> agent-platform/cloud-agents/handoff/cloud-to-cloud
  Mirrors the existing collapsible-group shape used by Triggers,
  Integrations, and Self-hosting in the same section.

src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx
- "(from the conversation details panel or the end-of-run tombstone)"
  -> "(from the conversation details panel or the artifacts shown
  after the run)". "Tombstone" is the internal code-level term for
  the post-run view (`shared_session/conversation_ended_tombstone_view.rs`).
  Even though it shows up in telemetry-event descriptions in
  `privacy.mdx`, it's not natural user-facing copy. Switched to a
  plainer reference to the artifacts surfaced after the run.

Validation
- python3 .agents/skills/style_lint/style_lint.py --changed -> 0 issues
  on the files this PR touches. (The pre-existing pricing-faqs.mdx
  warnings are out of scope.)
- python3 .agents/skills/check_for_broken_links/check_links.py
  --internal-only -> 0 broken (2,440 links, 322 files).
- `npm run build` fails on an UNRELATED orphan page
  (`agent-platform/cloud-agents/agents.mdx` is not registered in the
  sidebar). That page was added earlier on this branch by a different
  PR and is pre-existing breakage on `hyc/orch/handoff` — my edits
  don't touch it.

Co-Authored-By: Oz <oz-agent@warp.dev>